Management system and management method of computer system

ABSTRACT

A management system, which manages at least a computer system including a copy destination VOL, receives first performance related information including information related to a resource related to an operation with which a copy source VOL is associated as an I/O destination, and stores the received first performance related information. When an operation migrates from a first site to a second site (for example, when the first site is affected by a disaster), the management system reallocates a resource of the second site based on both the first performance related information and second performance related information including information related to a resource related to an operation originally executed at the second site among a resource group of the second site.

TECHNICAL FIELD

The present invention generally relates to management of a computersystem in a site, and to disaster recovery control, for example.

BACKGROUND ART

Disaster recovery is being adopted in an increasing number of cases.Disaster recovery refers to a mechanism in which a copy of data used byan operation (for example, a virtual machine) performed at a first site(a first computer system) is created at a remote second site (a secondcomputer system) and, upon loss of the data used by the operation, thecopy of the data is used to continue the operation at the second site.Generally, data copying for disaster recovery is realized by remotecopying that is performed as follows. Specifically, data stored in acopy source VOL (a primary VOL) owned by the first site is transferredto the second site and copied to a copy destination VOL (a secondaryVOL) in the second site. “VOL” is an abbreviation of a logical volume.Generally, a pair is constituted by one copy source VOL and one copydestination VOL. When there are a plurality of copy destination VOLswith respect to one copy source VOL, a plurality of pairs can becreated.

In addition, as an example of load balancing related to disasterrecovery, at least one of the sites including the first and second sitesconceivably has both a copy source VOL and a copy destination VOL.Specifically, for example, the first site includes a first copy sourceVOL and a second copy destination VOL. The second site includes a secondcopy source VOL which constitutes a pair with the second copydestination VOL (or a copy destination VOL of another site) and a firstcopy destination VOL which constitutes a pair with the first copy sourceVOL (or a copy source VOL of another site). Recently, there is anincrease in corporations using a plurality of sites in order to retaincontinuity of operations and such environments have become commonplace.

Normally, in such an environment, an allocated resource amount to a copysource VOL is large while an allocated resource amount to a copydestination VOL is small enough to enable processing of remote copying(writing).

PTL 1 discloses a technique for migrating data while taking anassociation between VOLs into consideration.

CITATION LIST Patent Literature

[PTL 1]

US2014/0129769

SUMMARY OF INVENTION Technical Problem

Unless a resource amount allocated to a component (for example, a copydestination VOL) related to an operation having migrated from a firstsite to a second site is increased at the second site, performance ofthe operation at the second site declines. This problem can be solved ifa configuration of the first site can be recreated at the second site.However, a resource group of the second site is limited and theconfiguration of the first site cannot always be recreated at the secondsite.

Solution to Problem

A management system, which manages at least a computer system includinga copy destination VOL, receives first performance related informationincluding information related to a resource related to an operation withwhich a copy source VOL is associated as an I/O destination, and storesthe received first performance related information. When the operationmigrates from a first site to a second site (for example, when the firstsite is affected by a disaster (or when another prescribed eventoccurs)), the management system reallocates a resource of the secondsite based on both the first performance related information and secondperformance related information including information related to aresource related to an operation originally being executed at the secondsite among a resource group of the second site. Resource reallocationmay be performed when a resource reallocation scheme is generated anddisplayed and an indication to execute the resource reallocation schemeis received from a user (for example, a manager) or may be performedwithout generating such a resource reallocation scheme.

Moreover, a first computer system (a computer system of the first site)may include a first host system executing a first operation (forexample, a virtual machine) and a first storage system providing aplurality of VOLs including a first VOL to be an I/O destination of thefirst operation. A second computer system (a computer system of thesecond site) may include a second host system executing a secondoperation and a second storage system providing a plurality of VOLsincluding a second VOL which constitutes a pair with the first VOL andwhich is a copy destination of the first VOL and a third VOL to be anI/O destination of the second operation. The first computer system mayinclude a first resource group, and the first host system and the firststorage system may have all of or a part of the first resource group. Atleast a part of the first resource group may be allocated to the firstoperation executed by the first host system and to the plurality of VOLsprovided by the first storage system. The second computer system mayinclude a second resource group, and the second host system and thesecond storage system may have all of or a part of the second resourcegroup. At least a part of the second resource group may be allocated tothe second operation executed by the second host system and to theplurality of VOLs provided by the second storage system.

Advantageous Effects of Invention

A decline in performance of an operation migrated from a first site to asecond site can be mitigated.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram showing an outline of an embodiment.

FIG. 2 is a configuration diagram of an example of a computer systemaccording to the embodiment.

FIG. 3 is a configuration diagram of an example of a configurationtable.

FIG. 4 is a configuration diagram of an example of a systemconfiguration table.

FIG. 5 is a configuration diagram of an example of a related site table.

FIG. 6 is a configuration diagram of an example of a function table.

FIG. 7 is a configuration diagram of an example of a performance historytable.

FIG. 8 is a configuration diagram of an example of a performance trendtable.

FIG. 9 is a configuration diagram of an example of an allocated resourcetable.

FIG. 10 is a configuration diagram of an example of a resource amounttable.

FIG. 11 is a configuration diagram of an example of a task table.

FIG. 12 is a flow chart of a pair configuration destination selectionprocess.

FIG. 13 is a flow chart of a performance related information extractionprocess.

FIG. 14 is a flow chart of a performance related information sharingprocess (copy source).

FIG. 15 is a flow chart of a pair configuration confirmation process.

FIG. 16 is a flow chart of an adjustment scheme generation process.

FIG. 17 is a flow chart of a resource adjustment process.

FIG. 18 is a configuration diagram of an example of an adjustment schemepresentation screen.

FIG. 19 is a configuration diagram of an example of an adjustment schemedetail screen.

FIG. 20 is a flow chart of a performance related information sharingprocess (copy destination).

DESCRIPTION OF EMBODIMENT

Hereinafter, an embodiment will be described.

Although information may sometimes be described below using expressionssuch as an “xxx table”, information may be expressed using any kind ofdata structure. In other words, an “xxx table” can also be referred toas “xxx information” in order to show that information is not dependenton data structure. In addition, in the following description, aconfiguration of each table represents an example and one table may bedivided into two or more tables and all of or a part of two or moretables may constitute one table.

Furthermore, while an ID or a name is used as identification informationof an element in the following description, other types ofidentification information may be used in place of, or in addition to,an ID or a name.

In addition, in the following description, when describing elements of asame type without distinguishing the elements from one another,reference signs or a common number in reference signs will be used.However, when describing elements of a same type by distinguishing theelements from one another, reference signs of the elements may be usedor IDs assigned to the elements may be used in place of the referencesigns of the elements. For example, when VOLs are to be describedwithout particularly distinguishing the VOLs from one another, adescription of “VOL 2210” may be used, and when individual VOLs are tobe described by distinguishing the VOLs from one another, a descriptionof “VOL 2201A” or “VOL #LV1” may be used.

In addition, in the following description, elements within a site X willbe denoted by a reference sign suffixed by X. For example, 2210A is areference sign of a VOL in a site A and 2210B is a reference sign of aVOL in a site B.

Furthermore, in the following description, an I/O (input/output) requestsignifies a write request or a read request and may also be referred toas an access request.

In addition, in the following description, a “storage unit” may be oneor more storage devices including a memory. For example, among a mainstorage device (typically, a volatile memory) and an auxiliary storagedevice (typically, a nonvolatile memory), a storage unit may at least bethe main storage device. Furthermore, a storage unit may include atleast one of a cache area (for example, a cache memory or a partial areathereof) and a buffer area (for example, a buffer memory or a partialarea thereof). A cache area and a buffer area may have a common point inthat data to be input to or output from a PDEV is temporarily storedtherein and may differ from each other on whether read data remains ornot. Specifically, data read from a cache area may remain in the cachearea but data temporarily read from a buffer area may not remain in thebuffer area.

In addition, in the following description, “PDEV” denotes a physicalstorage device and may typically be a nonvolatile storage device (forexample, an auxiliary storage device). For example, a PDEV may be an HDD(hard disk drive) or an SSD (solid state drive).

Furthermore, in the following description, “RAID” stands for a RedundantArray of Independent (or Inexpensive) Disks. A RAID group is constitutedby a plurality of PDEVs and stores data in accordance with a RAID levelassociated with the RAID group. A RAID group may also be referred to asa parity group. A parity group may refer to, for example, a RAID groupstoring parity.

In addition, while a “program” is sometimes used as a subject whendescribing a process in the following description, since a programcauses a prescribed process to be performed by appropriately using astorage resource (such as a memory) and/or an interface device (such asa communication port) and the like when being executed by a processor(such as a central processing unit (CPU)), a “processor” may be usedinstead as a subject of a process. A process described using a programas a subject may be considered a process performed by a processor or byan apparatus including a processor or may be considered a system.Furthermore, a processor may include a hardware circuit which performs apart of or all of a process. A program may be installed in an apparatussuch as a computer from a program source. The program source may be, forexample, a program distribution server or a storage medium that can beread by a computer. When the program source is a program distributionserver, the program distribution server includes a processor (forexample, a CPU) and a storage resource, and the storage resource mayfurther store a distribution program and a program that is adistribution target. Furthermore, by having the processor of the programdistribution server execute the distribution program, the processor ofthe program distribution server may distribute the program that is thedistribution target to other computers. In addition, in the followingdescription, two or more programs may be realized as one program or oneprogram may be realized as two or more programs.

Furthermore, in the following description, a management system may beconstituted by one or more computers. Specifically, for example, when amanagement computer displays information (specifically, for example,when a management computer displays information on its own displaydevice or when a management computer transmits information for displayto a remote display computer), the management computer constitutes amanagement system. In addition, for example, when functions identical orsimilar to those of a management computer are realized by a plurality ofcomputers, the plurality of computers (when a display computer performsdisplay, including the display computer) constitute a management system.A management computer (for example, a management system) may include aninterface device coupled to an I/O system including a display system, astorage resource (for example, a memory), and a processor coupled to theinterface device and the storage resource. The display system may be adisplay device included in the management computer or a display computercoupled to the management computer. The I/O system may be an I/O device(for example, a keyboard and a pointing device or a touch panel)included in the management computer or a display computer or anothercomputer coupled to the management computer. Moreover, a managementcomputer “displaying display information” may signify that displayinformation is displayed on the display system and may be performed bydisplaying display information on a display device included in themanagement computer or having the management computer transmit displayinformation to a display computer (in the case of the latter, displayinformation is to be displayed by a display computer). In addition, amanagement computer inputting or outputting information may signifyinputting or outputting information to or from an I/O display deviceincluded in the management computer or inputting or outputtinginformation to or from a remote computer (for example, a displaycomputer) being coupled to a management computer. Outputting informationmay signify displaying information.

In addition, in the following description, a “host system” may be asystem which transmits an I/O request to a storage system and mayinclude an interface device, a storage resource (for example, a memory),and a processor coupled to the interface device and the storageresource. The host system may be constituted by one or more hostcomputers. At least one host computer may by a physical computer and thehost system may include a virtual host computer in addition to aphysical host computer.

Furthermore, in the following description, a “storage system” may be oneor more storage apparatuses and may include a plurality of PDEVs (forexample, one or more RAID groups) and a storage controller forcontrolling I/O to and from the plurality of PDEVs. The storagecontroller may include a back end interface device coupled to theplurality of PDEVs, a front end interface device coupled to at least oneof a host system and a management system, a storage resource, and aprocessor coupled to the interface devices and the storage resource. Thestorage controller may be made redundant.

In addition, in the following description, “VOL” is an abbreviation of alogical volume and may be a logical storage device. A VOL may be a realVOL (RVOL) or a virtual VOL (VVOL). Furthermore, VOLs may include anonline VOL which is provided to a host system coupled to a storagesystem providing the VOL and an offline VOL which is not provided to ahost system (which is not recognized from the host system). “RVOL” maybe a VOL based on a physical storage resource (for example, one or moreRAID groups) included in a storage system that includes the RVOL. A“VVOL” may be at least one of an externally coupled VOL (EVOL), acapacity expanded VOL (TPVOL), and a snapshot VOL. An EVOL may be a VOLbased on a storage resource (such as a VOL) of an external storagesystem and in accordance with storage virtualization technology. A TPVOLmay be a VOL constituted by a plurality of virtual areas (virtualstorage areas) and in accordance with capacity virtualization technology(typically, thin provisioning). A snapshot VOL may be a snapshot VOLprovided as a snapshot of an original VOL. A TPVOL may typically be anonline VOL. A snapshot VOL may be an RVOL. A “pool” refers to a logicalstorage area (for example, a set of a plurality of pool VOLs) and may beprepared for each use. For example, pools may include at least one of aTP pool and a snapshot pool. ATP pool may be a storage area constitutedby a plurality of real areas (real storage areas). A real area may beallocated from a TP pool to a virtual area of a TPVOL. A snapshot poolmay be a storage area in which data saved from an original VOL isstored. One pool may be used as a TP pool and a snapshot pool. A “poolVOL” may refer to a VOL to be a component of a pool. A pool VOL may bean RVOL or an EVOL. A pool VOL may typically be an offline VOL.

In addition, in the following description, a “resource” refers to aphysical or a virtual element of a physical or a virtual apparatus ordevice. Examples of a physical element may include a CPU, a CPU core, amemory, a PDEV, a RAID group, and an I/O device (for example, aninterface device). Examples of a virtual element may include a virtualCPU, a virtual CPU core, and a virtual memory. In the followingdescription, a physical or a virtual apparatus or device to which aresource is allocated may be collectively referred to as a “component”.

FIG. 1 is a diagram showing an outline of the embodiment.

As an example of a plurality of sites, three sites #A to #C (sites 101Ato 101C) are provided.

The site #A includes a computer system and a management server 1000A.The computer system in the site #A includes a storage apparatus 2000Aand a server (a physical server) 3000A which inputs and outputs data toand from the storage apparatus 2000A via a communication network such asa data network (for example, a SAN (storage area network)) 4000A. Thestorage apparatus 2000A includes one or more VOLs 2210A. The computersystem is managed by the management server 1000A.

A configuration of the site #B is substantially similar to aconfiguration of the site #A. A storage apparatus 2000B is coupled tothe storage apparatus 2000A via a data network 4000AB so as to becapable of communication. Moreover, when a suffix of a reference sign isa set of two or more alphabetical characters among A to C, an elementdenoted by the reference sign is assumed to be an element shared by twoor more sites corresponding to the two or more alphabetical characters.The element may not exist in any of the sites or may exist outside anyof the sites.

The site #C does not include a computer system and may include amanagement server 1000C capable of communicating with the managementserver 1000 in at least one of the other sites #A and #B.

In the present embodiment, the server 3000 is an example of a hostcomputer. The storage apparatus 2000 is an example of a storage system.The management server 1000 may be an example of a management system (amanagement computer) or a set of the management servers 1000A to 1000Cmay be an example of a management system. There may be an integratedmanagement server coupled to the management servers 1000A to 1000C, inwhich case the integrated management server or a system including atleast one management server 1000 and the integrated management servermay be an example of the management system.

In the present embodiment, for example, the following processes (1) to(3) are executed.

(1) The management server 1000A (a pair selection program 1150A) refersto configuration information repositories 1110B and 1110C included inmanagement servers 1000B and 1000C of the remote sites #B and #C uponconstructing a pair of VOLs, and selects a site which is functionallyusable as a copy destination site. Let us assume that, at this point,the site #B is selected as the copy destination site and, consequently,a VOL #LV3 is selected as a copy destination VOL of a copy source VOL#LV1.

(2) During operation of a pair, the management server 1000A (a sharingprogram 1180A) periodically or non-periodically extracts informationrelated to the copy source VOL #LV1 from a performance informationrepository 1120A of the management server 1000A. The management server1000A (the sharing program 1180A) shares first performance relatedinformation including the extracted information with at least the site#B which manages the copy destination VOL #LV3 among the other sites #Band #C (provides the first performance related information including theextracted information to a sharing program 1180B in a management server1000B). Moreover, after start of operation of the pair, data is remotelycopied from the VOL #LV1 to the VOL #LV3. The remote copying may beremote copying performed in synchronization with processing of a writerequest from the server 3000A or may be remote copying performedasynchronously with the processing of a write request from the server3000A (for example, remote copying using a so-called journal).

(3) Let us assume that, due to the site #A being affected by a disaster,an operation #1 (for example, a virtual machine) of the server 3000Amigrates to a server 3000B and, as a result, an I/O destination of dataaccompanying the operation switches from the copy source VOL #LV1 to thecopy destination VOL #LV3. In this case, in the management server 1000Bin the original copy destination site #B, the sharing program 1180Bextracts the shared first performance related information from theoriginal copy source site #A (the site #A prior to the disaster). Anadjustment scheme generation program 1190B generates and displays anadjustment scheme for resource allocation of the site #B based on theextracted first performance related information and on secondperformance related information including information related to aresource related to an operation #2 originally executed at the site #B.In this case, an “adjustment for resource allocation” refers toreallocation of a resource of a migration destination site (#B) of anoperation. In other words, an “adjustment for resource allocation”refers to changing a correspondence between a component in a migrationdestination site and a resource in the migration destination site.

When a copy source site is affected by a disaster, a previous operatingstate of the copy source site cannot be comprehended. Attempting tostore all performance history of all sites before a disaster occurs maycreate a situation where a management cycle involving collecting dataand processing of collected data (for example, analyzing data andstoring the data in a database (DB)) cannot be properly performed dueto, for example, arrival of a next collection process start timingbefore processing of all collected information is completed.

According to the present embodiment, since the process (2) describedabove is performed, even if the copy source site is affected by adisaster, a past performance-related state of the copy source site (forexample, a time series variation of a performance value with respect toa resource (element) related to an operation) can be comprehended.Therefore, when restarting an operation of a disaster-affected copysource site at a copy destination site, it is expected that anappropriate resource for the operation that is a restart object can beallocated within a range of resource limitations of the copy destinationsite.

Hereinafter, a configuration of a site will be described mainly usingsites #A and #B as an example. At least two sites among a plurality ofsites may have a same configuration. With respect to a certain pair, aconfiguration (for example, a type, number, amount, or performance ofresources) of a resource group of a computer system of a site (forexample, the site #A) to be a copy source may differ from aconfiguration of a resource group of a computer system of a site (forexample, the site #B) to be a copy destination.

FIG. 2 is a configuration diagram of the site #A.

The site includes the management server 1000A, the storage apparatus2000A, and the server 3000A. There may be one or more of at least one ofthese elements. The server 3000A and the storage apparatus 2000A arecoupled to each other via the data network (for example, an FC (FibreChannel) network) 4000A. The management server 1000A, the storageapparatus 2000A, and the server 3000A are coupled to each other via amanagement network (for example, an IP (Internet Protocol) network)5000.

The management server 1000A includes a memory 1100A, an interface device(I/F) 1200A, a CPU 1300A, an output device 1400A, an input device 1500A,and a PDEV 1600A, which are coupled to each other via an internal bus1700A.

The memory 1100A stores a configuration information repository 1110A, aperformance information repository 1120A, a task table 1130A, a resourceadjustment scheme table 1140A, a pair selection program 1150A, a pairgeneration program 1160A, an extraction program 1170A, a sharing program1180A, an adjustment scheme generation program 1190A, an adjustmentscheme presentation program 11A0A, a resource adjustment program 11B0A,a task adjustment program 11C0A, and a pair confirmation program 11D0A.

The configuration information repository 1110A includes a configurationtable 1111A, a system configuration table 1112A, a related site table1113A, and a function table 1114A. The configuration table 1111A managesinformation indicating a component/resource existing on an I/O routebetween the server 3000A and a logical space 2220A associated with a VOL(in other words, information indicating a coupling relationship of acomponent/resource on an I/O route). The system configuration table1112A manages information related to a VM system which is a set of oneor more VMs (virtual machines). The system configuration table 1112A maymanage information related to a component system (a set of one or morecomponents of a same type) other than a VM system.

The related site table 1113A manages information related to themanagement servers 3000B and 3000C (for example, IP addresses andauthentication information of the management servers) of the other sites#B and #C. The function table 1114A manages information related to afunction in the site (for example, information indicating a function ofa storage apparatus or a server (for example, a snapshot function or acapacity virtualization (for example, thin provisioning) function) andinformation representing whether or not the function is to be used whenaffected by a disaster or the like).

The performance information repository 1120A includes a performancehistory table 1121A, a performance trend table 1122A, an allocatedresource table 1123A, and a resource amount table 1124A. The performancehistory table 1121A manages, in a time series, performance informationwith respect to a monitoring target (for example, an apparatus and eachdevice in an apparatus (a program executed by an apparatus may beincluded)) which is coupled to the data network 4000A.

The performance trend table 1122A manages a trend in performance relatedto a work load in units such as monthly or weekly. The allocatedresource table 1123A manages an amount of resources allocated to amonitoring target. The resource amount table 1124A manages an amount ofhardware resources of a monitoring target. For example, the resourceamount table 1124A manages computing resources of a server such as thenumber of CPUs, a memory capacity, a network bandwidth, and a PDEVcapacity. The task table 1130A manages information related to a task ateach site (for example, starting acquisition of backup of a VOL at23:00). The resource adjustment scheme table 1140A manages informationindicating a resource allocation adjustment scheme (hereinafter, alsoabbreviated as an “adjustment scheme”) generated by the adjustmentscheme generation program 1190A.

The I/F 1200A is a device for coupling to the management network 5000.The CPU (for example, a CPU) 1300A executes a program deployed on thememory 1100A. The output device 1400A is a device such as a displaydevice which outputs a result of processing (for example, a result ofexecution of the adjustment scheme presentation program 11A0A) executedby the management server 1000A. The input device 1500A is a device (forexample, a keyboard) used by a manager to input an indication to themanagement server 1000A. The PDEV 1600A is, for example, an HDD or anSSD.

While the programs and the tables are stored in the memory 1100A in theexample shown in FIG. 2, alternatively, the programs and the tables maybe stored in the PDEV 1600A or in another storage medium (not shown). Inthis case, when executing a target program, the CPU 1300A reads theprogram onto the memory 1100A and executes the read program.

Alternatively, the programs and the tables described above may be storedin a memory 2100A of the storage apparatus 2000A or in a memory 3100A ofthe server 3000A and the storage apparatus 2000A or the server 3000A mayexecute a stored program. Alternatively, another apparatus such asanother server 3000A or a switch (not shown) may store the programs andthe tables described above and execute a stored program. The managementserver 1000A can communicate with a program running on the server 3000Athrough the management network 5000.

The storage apparatus 2000A includes a VOL providing unit 2200A and astorage controller coupled thereto. The VOL providing unit 2200A is aPDEV group and may be, for example, one or more RAID groups. The storagecontroller includes the memory 2100A, a PDEV I/F 2300A, a management I/F2400A, a CPU 2500A, and a storage I/F 2600A, which are coupled via acommunication path 2700 that is an internal bus or the like.

The memory 2100A includes a cache area 2110A. In addition, the memory2100A stores a collection program 2120A. The cache area 2110A is astorage area for temporarily storing information. The collection program2120A is a program for transmitting and receiving managementinformation, performance information, and the like of the storageapparatus 2000A to and from the management server 1000A.

The VOL providing unit 2200A includes the logical space 2220Aconstituted by storage areas of one or more PDEVs (not shown). A VOL2210A is a storage area obtained by logically dividing the logical space2220A. Accordingly, access to the VOL 2210A from an external apparatusof the storage apparatus 2000A is enabled. Moreover, a space ID isassigned to the logical space 2220A and a VOL ID is assigned to the VOL2210A. Accordingly, the storage apparatus 2000A can respectivelyuniquely identify the logical space 2220A and the VOL 2210A.

The PDEV I/F 2300A is an interface device for coupling to the VOLproviding unit 2200A. The management I/F 2400A is an interface devicefor coupling to the management network 5000. The CPU 2500A executes aprogram deployed on the memory 2100A. The storage I/F 2600A is aninterface device for coupling to the data network 4000A. While thecollection program 2120A is stored in the memory 2100A in the exampleshown in FIG. 2, alternatively, the collection program 2120A may bestored in another storage area (not shown). In this case, when executinga process, the CPU 2500A reads the collection program 2120A onto thememory 2100A and executes the collection program 2120A.

Alternatively, the collection program 2120A may be stored in the memory1100A of the management server 1000A and the management server 1000A mayexecute the stored program 2120A. Alternatively, another storageapparatus (for example, B or C) may store the collection program 2120Aand may execute the stored program 2120A. In addition, the VOL providingunit 2200A may create a single VOL 2210A using an entire storage area ofthe single logical space 2220A.

The server 3000A includes the memory 3100A, a server I/F 3200A, a CPU3300A, and a management I/F 3400A, which are coupled via a communicationpath 3500 that is an internal bus or the like.

The memory 3100A stores a collection program 3110A, an operation program3120A, a VOL management program 3130A, and a path management program3140A.

The collection program 3110A is a program for transmitting and receivingperformance information and the like of the server 3000A to and from themanagement server 1000A. The operation program 3120A is a program (forexample, a DBMS (Database Management System), a file system, or a VMwhich executes these systems) for realizing an operation to be executedby the server 3000A. The VOL management program 3130A is a program forallocating the VOL 2210A provided by the storage apparatus 2000A to theserver 3000A. The server 3000A executes various operations using the VOL2210A provided by the storage apparatus 2000A. The path managementprogram 3140A is a program for managing a state of a path between theserver 3000A and the VOL 2210A.

While the programs are stored in the memory 3100A in the example shownin FIG. 2, the programs may be stored in another storage area (notshown). In this case, when executing a process, the CPU 3300A reads atarget program on the memory 3100A and executes the read program.

In the example shown in FIG. 2, the server 3000A and the storageapparatus 2000A are coupled to each other via the data network 4000A.

The coupling between the storage apparatus 2000A and the server 3000A isnot limited to a direct coupling via a fiber channel and may be acoupling via one or more network devices such as a fiber channel switch.In addition, the coupling between the storage apparatus 2000A and theserver 3000A need only be a network for data communication and may be anIP (Internet Protocol) network.

FIG. 3 is a configuration diagram of an example of the configurationtable 1111A.

The configuration table 1111A includes information related to an I/Opath to the logical space 2220A which constitutes the VOL 2210A providedto the server 3000A and information related to a VOL which forms a copypair with the VOL 2210A. Specifically, for example, the configurationtable 1111A has a record for each VM (virtual machine: in other words,each operation) executed in the server 3000A. Each record storesinformation such as a server 110A, a VM 111A, a drive 112A, a serverdata I/F 113A, a storage 114A, a storage data I/F 115A, a CPU 116A, aVOL 117A, a logical space 118A, a pair partner site 119A, a pair partnerstorage 120A, and a pair partner VOL 121A.

The server 110A is an ID of the server 3000A. The VM 111A is an ID of aVM. The drive 112A is an ID for uniquely identifying, in the server3000A, a mount point of the server 3000A. The server data I/F 113A is anID of the server I/F 3200A which is used when a VM accesses the VOL2210A indicated by the VOL 117A. The storage 114A is an ID of thestorage apparatus 2000A to be an access destination of a VM.

The storage data I/F 115A is an ID of the storage I/F 2600A which isused when a VM accesses the VOL 2210A indicated by the VOL 117A.

The CPU 116A is an ID of the CPU 1300A which is used when a VM accessesthe VOL 2210A indicated by the VOL 117A. The VOL 117A is an ID of theVOL 2210A. The logical space 118A is an ID of the logical space 2220Aincluding the VOL 2210A indicated by the VOL 117A. The pair partner VOL121A, the pair partner storage 120A, and the pair partner site 119A are,respectively, an ID of a VOL which forms a copy pair with the VOL 2210Aindicated by the VOL 117A, an ID of a storage apparatus including theVOL, and an ID of a site including the VOL.

The pieces of information 119 to 121 may be information collected from acomputer system.

In this case, while the configuration table 1111A includes informationof the server 3000A, the storage apparatus 2000A, and the like asapparatuses and devices existing on an access path, the information inthe configuration table 1111A is not limited thereto. For example, theconfiguration table 1111A may include information of a switch, a dataI/F of the switch, and the like, and information regarding a program (aDBMS or the like) on the server 3000A, a snapshot VOL which stores asnapshot of a VM, a clone VOL which stores a clone, and the like may beassociated with the configuration table 1111A.

FIG. 4 is a configuration diagram of an example of the systemconfiguration table 1112A.

The system configuration table 1112A stores information related to a VMsystem. For example, a VM system may be a set of one or more VMs (forexample, operation programs). An example of a VM system is, forinstance, a web 3-tier system which is a set of 3 VMs. For example, thesystem configuration table 1112A has a record for each VM system.

Each record stores a system ID 120A, an importance 121A, and a VM IDserver 122A. The system ID 120 is an ID of a system. The importance 121Ais information indicating an importance of a VM system. While theimportance is any of three levels of “high”, “middle”, and “low”, theremay be more levels or there may only be two levels. The VM ID 122 is oneor more IDs respectively corresponding to one or more VMs constituting aVM system.

FIG. 5 is a configuration diagram of an example of the related sitetable 1113A.

The related site table 1113A stores information on a related site thatis a site which may be a copy destination of the site #A.

Specifically, for example, the related site table 1113A has a record foreach related site. Each record stores a site ID 130A, a coupling 131A, atime point difference 132A, and management format information 133A. Thesite ID 130A is an ID of a related site. The coupling 131A isinformation necessary to access the related site (for example, an IPaddress of a management server in the related site). Information capableof identifying a related site may be other information in place of or inaddition to at least one of the site ID 130A and the coupling 131A. Thetime point difference 132A is information indicating a differencebetween a current time point at the site #A and a current time point atthe related site. The time point difference 132 may be, for example, avalue calculated using time points acquired from respective NTP (networktime protocol) servers or the like of the site #A and the related site.The management format information 133A is information related to amanagement format and may be, for example, a type, a version, and thelike of a management program (for example, a package of programs 1150 to11D0) used at the related site.

FIG. 6 is a configuration diagram of an example of a function table1114B.

The function table 1114B stores information related to functions of thesite #B. Specifically, for example, the function table 1114B has arecord for each function of the site #B. Each record stores a functionname 140B, a component ID 141B, a specific name 142B, a usability 143B,and a target site 144B. The function name 140B is a name of a function.In this case, the function name 140B may be a generic name instead of aspecific name of the function. For example, a value of the function name140B may be “Thin Provisioning”, “Snapshot”, or the like as a namespecified in SMI-S(Storage Management Initiative Specification) which isa standard specification of storage management or in a CIM (CommonInformation Model) which is a standard model of system management. Thecomponent ID 141B is an ID of a component (an apparatus or a device).The specific name 142B represents a specific name of the function. Theusability 143B is information indicating whether or not there is apossibility of an operation (a valid operation) running at another site(#A) during a normal operation being used at the site #B when the othersite (#A) is affected by a disaster. The target site 144B is an ID of asite using a same function (a site at which a same function is enabled).Information regarding the usability 143B and the target site 144B may betransmitted from a management server 3000A of the copy source site #Aand stored in the management server 3000B of the copy destination instep 8113 of the pair configuration destination selection process 8100by the pair selection program 1150A.

FIG. 7 is a configuration diagram of an example of the performancehistory table 1121A.

The performance history table 1121A stores, in a time series,performance information of a monitoring target (for example, acomponent/resource) such as performance information related to the VOL2210A, the logical space 2220A, and the like of each storage apparatus2000A. The performance history table 1121A has a record for each timepoint. Each record stores a time point 210A, an apparatus ID 211A, adevice ID 212A, and performance data (a metric 213A and a performancevalue 214A). The time point 210 indicates a time point at whichperformance data had been collected. The apparatus ID 211 is an ID of anapparatus including the monitoring target. The device ID is an ID of adevice as the monitoring target.

The metric 213 indicates a type of a performance value in performancedata (for example, an I/O amount per IOPS (a frequency of I/O (a unittime such as 1 second)) with respect to a VOL). The performance value214 is a value of performance (for example, a measured value).

While the monitoring target is a VOL in FIG. 7, the monitoring targetmay be, in place of or in addition to a VOL, another element such as thestorage I/F 2600A, the logical space 2220A, the server I/F 3200A, and aPDEV. In addition, while the metric is IOPS in FIG. 7, the metric maybe, in place of or in addition to IOPS, CPU usage, a response time (atime length from receiving a request to returning a response), an I/Obusy rate, a transfer rate, or a throughput.

Furthermore, with respect to a DBMS, the metric may be a buffer hitrate, the number of inserted records, the number of updated records, thenumber of deleted records, and the like. Moreover, the metric may be aresponse time of a web server, free capacity or a utilization rate of afile system or a PDEV, an amount of input/output data, the number oferrors occurring at a network interface, a buffer overflow, a frameerror, or the like.

FIG. 8 is a configuration diagram of an example of the performance trendtable 1122A.

The performance trend table 1122A manages a monitoring target and atrend in performance related to a work load in units such as monthly,weekly, or daily of the monitoring target. For example, a plurality ofperformance level values are prepared in accordance with a value ofIOPS. A performance level value is a grade (a level value) to which aperformance value (for example, a value of IOPS) belongs. For example,IOPS “0”=performance level value “0”, IOPS “0 to 10 K”=performance levelvalue “1”, and IOPS “10 K to 20 K”=performance level value “2”. In otherwords, a performance value condition is associated with each performancelevel value. A performance value condition may be a set of a metric anda performance value range.

Time series information and information indicating which performancelevel value a performance value belongs to are managed as trendinformation of each device in the monitoring target. For example, AM00:00 to AM 08:00 is managed as belonging to performance level value 0,AM 08:00 to AM 8:30 as belonging to performance level value 1, AM 08:30to PM 05:30 as belonging to performance level value 2, and PM 05:30 toPM 24:00 as belonging to performance level value 1.

At least a part of the performance trend table 1122A may represent anexample of first performance related information. Information related toa VM system that is a migration target among the performance trend table1122A may be transmitted to a management server of a site that is amigration destination and stored in the migration destination site bythe management server of the migration destination site.

The performance trend table 1122A has a record for each monitoringtarget. Each record stores an apparatus ID 220A, a device ID 221A, ametric 222A, a performance level value 223A, a time 224A, and a minimumoperation value 225A. The apparatus ID 220A is an ID of an apparatusincluding the monitoring target. The device ID 221A is an ID of a deviceas the monitoring target. The metric 222A indicates a type of aperformance value. The performance level value 223A is a performancelevel value. The time 224A indicates a time slot. A correspondencebetween the performance level value 223A and the time 224A is determinedaccording to a performance value condition of the performance levelvalue and which performance value condition a value (for example, amaximum value, a minimum value, or an average value) based on aperformance value acquired in the time slot corresponds to. The numberof performance level values and a performance value condition which isassociated with a performance level value may be fixed values preparedin advance or may be dynamically divided in accordance with theperformance value 214A in the performance history table 1121A. Theminimum operation value 225A indicates a minimum required performancevalue with respect to a device. For example, an IOPS or the like whichoccurs when starting up a VM may be the minimum operation value 225A.

The performance trend table 1122A is a result of a reduction of a dataamount of the performance history table 1121A by normalization or thelike. While a data amount is reduced by dividing according toperformance level values in this case, a data amount may be reduced byprocessing the performance history table 1121A based on other rules inplace of or in addition to dividing according to performance levelvalues.

FIG. 9 is a configuration diagram of an example of the allocatedresource table 1123A.

The allocated resource table 1123A manages an amount of resourcesallocated to a monitoring target (for example, a component). Theallocated resource table 1123A has a record for each component. Eachrecord stores an apparatus ID 240A, a device ID 241A, and an allocatedresource amount 242A. While a CPU core and a memory are adopted as typesof resources to be allocated in the example shown in FIG. 9, resourcetypes need not be limited to a CPU core and a memory. The apparatus ID240A is an ID of an apparatus including the component.

The device ID 241A is an ID of a device as the component. The allocatedresource amount 242 indicates an amount of allocated virtual resourcesand includes, for example, the number of CPU cores 243 and a memoryamount 244. The number of CPU cores 243 indicates the number of virtualCPU cores allocated to the device. The memory amount 244 indicates anamount of virtual memory (a virtual storage capacity) allocated to thedevice. A resource allocated to a VM may be a CPU usage, a bandwidth ofthe storage I/F 2600A, or the like in addition to (or in place of) a CPUcore and a memory amount.

As an example, a system #Y is constituted by a VM #5, a VM #7, and a VM#8 (refer to FIG. 4). In this case, according to the allocated resourcetable 1123A, the numbers of CPU cores allocated to these VM are 2, 2,and 4, and the memory amounts allocated to these VM are 8 GB, 8 GB, and16 GB. Generally, for example, when respectively preparing VMs having aplurality of roles in a web 3-tier system, resource allocation is oftendesigned in accordance with intended use and a processing of each VMsuch as a web server (VM) which performs a response process with respectto a request from a web browser, an application server (VM) whichperforms an arbitrary operation process, and a database server (VM)which performs reference and update processes of data. The allocatedresource table 1123A may be constructed based on such designs.

FIG. 10 is a configuration diagram of an example of the resource amounttable 1124A.

The resource amount table 1124A manages an amount of resources of amonitoring target (for example, a component). Each record of theresource amount table 1124A stores an apparatus ID 300A, a device ID302, a resource type 303, and a resource restriction 304. The apparatusID 300A is an ID of an apparatus. The device ID 302A is an ID of adevice. The resource type 303A indicates a type of a resource (forexample, a physical resource). The resource restriction 304A indicates amaximum usable amount of a resource.

The resource restriction 304A may be a physical restriction (forexample, the number of resources in an apparatus) or a logicalrestriction (for example, a threshold set by a user (for example, amanager)). At least a part of the resource amount table 1124A mayrepresent an example of first performance related information.

Information related to a VM system that is a migration target among theresource amount table 1124A may be transmitted to a management server ofa site that is a migration destination and stored by the managementserver of the migration destination site.

For example, when the server #A has eight CPU cores, the resourcerestriction 304 corresponding to the resource type 303A “number of CPUcores” of the server #A is “8”. When an IOPS limit value of hardwarespecifications of a CPU #4 of the storage apparatus #A is 80 K, “IOPS”is stored as the resource type 303 and “80 K” is stored as the resourcerestriction 304A. While the resource restriction 304A is a maximumusable resource amount in this case, a statically or dynamicallydetermined resource amount threshold may be adopted instead of a maximumresource amount.

FIG. 11 is a configuration diagram of an example of a task table 1130B.

The task table 1130B has a record for each task which may be executed atthe site #B. Each record stores a start time point 400B, an estimatedend time point 401B, an option 402B, a task name 403B, and a target404B. The start time point 400B indicates a start time point of a task.The estimated end time point 401B indicates an estimated end time pointof the task. The option 402B indicates an execution option of the task(for example, a task executed only once or a task executed periodicallyand repetitively). For example, in the case of a task that is executedat a same time point every day, the option 402 is “Daily”. The task name403 indicates a name of a type (for example, “Backup” or “VM migration”)of the task (function). The target 404 indicates an ID of a target (forexample, a device or an apparatus) at which a process is executed by thetask.

Next, processes executed by the management server 1000A of the copysource site #A or the management server 1000B of the copy destinationsite #B will be described.

The plurality of processes are roughly classified into the three timings(phases) described below.

(Timing 1) Upon introduction of system (in other words, upon pairconstruction for a disaster configuration). The process shown in FIG. 12is executed by the management server 1000A.(Timing 2) During normal operation of system. The processes shown inFIGS. 13, 14, 15, and 20 are executed by the management servers 1000Aand 1000B. For example, the processes are periodically executed.(Timing 3) Upon occurrence of system failure (in other words, afteroccurrence of disaster). The processes shown in FIGS. 16 and 17 areexecuted by the management server 1000B.

FIG. 12 is a flow chart of a pair configuration destination selectionprocess.

A pair configuration destination selection process 8100 is a process ofselecting a pair configuration destination which does not pose a problemeven when operations are switched in accordance with an occurrence of adisaster, and configuring a pair. The present process 8100 is executedby the pair selection program 1150A and the pair generation program1160A.

First, the pair selection program 1150A receives an input of informationon a copy source (step 8101). Any means may be adopted as long as thepair selection program 1150A can receive information on the copy source.For example, the pair selection program 1150A may receive informationspecified by the user via the input device 1500A. In addition, theinformation on the copy source may include an ID of a copy source VOL.In step 8101, the VM 1111A corresponding to the VOL 117 which matchesthe ID of the copy source VOL may be identified from the configurationtable 1111A, and the system 120A corresponding to the systemconfiguration server 122A which matches the VM 111A may be identifiedfrom the system configuration table 1112A.

Next, the pair selection program 1150A refers to the related site table1113A and identifies a site (a related site) which is capable ofconstructing a pair relationship with the copy source specified in step8101 (step 8102).

Next, based on information on the related site identified in step 8102,the pair selection program 1150A performs steps 8103 to 8107 describedbelow for each related site (loop A). “Site #B” will be described as anexample of one of the related sites. In step 8103, the pair selectionprogram 1150A acquires configuration information to be used as a pairconstruction condition from the configuration information repository1110B in the management server 1000B of the site #B. Examples ofconfiguration information to be used as a pair construction conditioninclude: (a) information indicating that a line for transferringinformation on a pair has already been physically laid and aconfiguration for data transfer has been performed; (b) informationindicating a configuration for difference management in order toguarantee consistency in data transfer of a pair has been performed; (c)information indicating that software (a program) for remote copying hasbeen installed; (d) information indicating that a VOL usable as a copydestination of remote copying exists; and (e) information indicatingthat writing by a remote copying process can be performed withoutincident at the copy destination during normal operation. In step 8104,the pair selection program 1150A determines whether or not a pair can beconstructed with the copy source input in step 8101 based on theconfiguration information acquired in step 8103, and selects aconfigurable pair destination candidate. When a result of thedetermination in step 8104 is positive, in step 8105, the pair selectionprogram 1150A acquires function information from the function table1114B of the configuration information repository 1110B. In step 8106,the pair selection program 1150A determines whether or not a functionthat can be provided at the copy source can be provided in a similarmanner at the copy destination selected as being capable of constructinga pair based on the function information acquired in step 8105, andselects a pair destination candidate capable of providing the function.For example, when a CoW (Copy on Write) function has been provided as asnapshot function at the storage apparatus #A that is a copy source, thepair selection program 1150A selects a storage apparatus #X (one of thestorage apparatuses in the site #B) having a similar function as thepair destination (refer to FIG. 6). In step 8107, the pair selectionprogram 1150A stores the pair destination selected in step 8106 as apair destination candidate. In addition, for example, the pair selectionprogram 1150A also selects a configuration capable of using a server #Ehaving a VM Snapshot function which is a function of a similar type as apair destination candidate. While a determination is made in this casebased on whether or not a providable function can be provided,alternatively, a determination may be made based on whether or not afunction actually being used at the copy source can be managed and theused function can be provided in a similar manner. When a pairdestination candidate satisfying conditions does not exist in step 8104and step 8106, the check with respect to the site #B is ended and atransition is made to a check with respect to another related site (loopA).

Next, the pair selection program 1150A determines whether or notinformation on the pair destination candidate stored in step 8107 exists(step 8108). When a result of the determination in step 8108 isnegative, the pair selection program 1150A presents the user with thenegative result (step 8109). Based on this information, the user canconfirm the pair construction condition and function and subsequentlytake measures such as changing configurations or the like. When theresult of the determination in step 8108 is positive, the pair selectionprogram 1150A presents the user with pair destination candidates(displays display information related to the pair destinationcandidates) and accepts an input on which of the pair destinationcandidates is to be selected (step 8110). At this point, for example,the pair selection program 1150A receives information specified by theuser from the input device 1500A. In step 8111, the pair selectionprogram 1150A checks for input. When there is no input, the pairselection program 1150A ends the pair configuration destinationselection process 8100, but when there is an input, the pair selectionprogram 1150A advances to step 8112.

As the determination in step 8111, the selection process may be endedwhen there is no input for a prescribed time or the selection processmay be ended when there is an input to end the selection process.

In addition, while a presentation is made and an input is accepted instep 8110 in this case, alternatively, the process of step 8110 may beomitted, a pair destination candidate may be automatically selected andinput in the process of step 8111 based on a policy such as “Prioritizesite #B”, “Prioritize a pair destination candidate of which functioninformation matches completely”, and “Random sampling”, and the pairselection program 1150A may proceed to a next step.

Next, in step 8112, based on the input, the pair selection program 1150Atransmits an execution request to the pair generation program 1160A. Thepair generation program 1160A executes pair generation based on thespecified information. Since the pair generation process is a generalprocess, a description thereof will be omitted.

Next, in step 8113, the pair selection program 1150A transmits functioninformation that may possibly be used by the generated pair to themanagement server (for example, 1000B) of the copy destination site (forexample, the site #B). When receiving the function information, themanagement server (for example, a CPU 1300B) of the copy destinationupdates the usability 143B and the target site 144B (information in thefunction table 1114B) which correspond to the function indicated by thefunction information. For example, the usability 143B is updated to“Yes” and the target site 144 is updated to “site A”. Due to suchupdating, when an attempt to change the function is made at the site B,the management server 1000B can take an action such as displaying awarning to the effect that the function may possibly be used in thefuture by a pair formed with the site A that is the copy source.

FIG. 13 is a flow chart of a performance related information extractionprocess.

A performance related information extraction process 8200 is a processof extracting performance trend information from performance information(a set of a metric and a performance value corresponding to a monitoringtarget in the performance history table 1121A) of a monitoring targetand, together with a resource amount allocated to the monitoring targetand the like, extracting information related to performance of eachsystem. The present process is repetitively (for example, periodically)performed by the extraction program 1170A.

First, the extraction program 1170A performs steps 8201 to 8203 (loop B)for each component (monitoring target) identified from the configurationtable 1112A. Hereinafter, the “VOL #LV5” will be described as an exampleof a monitoring target. The extraction program 1170A refers to theperformance history table 1121A with respect to the VOL #LV5 (step8201). The extraction program 1170A acquires information (the time point210A, the apparatus ID 211A, the metric 213A, and the performance value214A) from each record including the device ID 212A “VOL #LV5”.Subsequently, the extraction program 1170A generates a performance trendbased on the acquired information and stores the generated performancetrend in the performance trend table 1122A (step 8202). For example, theextraction program 1170A aggregates history with respect to an IOPS(metric) of the “VOL #LV5”. Time “00:00 to 08:00” is associated with theperformance level value “0” since there was no I/O. Time “08:00 to08:30” and time “17:30 to 24:00” are associated with the performancelevel value “1” since I/O ranged from “0 to 10 K” on average. Time“08:30 to 17:30” is associated with the performance level value “2”since I/O ranged from “10 to 20 K” on average. In this manner, whengenerating a performance trend, a plurality of time slots are associatedwith a plurality of performance level values. While a performance trendis generated as a daily trend in 30-minute units in this case, aperformance trend may be generated as a daily trend in 1-hour units oras a weekly or monthly trend. Subsequently, the extraction program 1170Adetermines a minimum value necessary for operation and stores thedetermined value as the minimum operation value 225 in the performancetrend table 1122 (step 8203). For example, the minimum value necessaryfor operation may be determined based on performance history uponstartup (for example, a startup time point identified based on a startupschedule or the like and history identified based on the time point 210Ain the table 1121A).

Next, the extraction program 1170A refers to the system configurationtable 1112A (step 8204) and performs step 8205 for each VM system (loopC). Specifically, the extraction program 1170A refers to the allocatedresource table 1123A and the performance trend table 1122A with respectto a VM system and stores a set of a performance trend and an allocatedresource amount of each VM in the VM system (step 8205). In the presentprocess 8200, by storing or using information in the performance trendtable 1122A shown in FIG. 8 or the resource table 1123A shown in FIG. 9in units of monitoring targets in a same system in the systemconfiguration table 1112A shown in FIG. 4, information which had beendesigned at the copy source site (or accumulated through operation atthe copy source site) and which is necessary to operate the VM systemwithout incident (in other words, information indicating a resourceamount ratio of a VM) can be utilized. In step 8205, the importance 121Ain FIG. 4 may be stored in association with the set of the performancetrend and the allocated resource amount. In addition, in the presentprocess 8200, when the copy source site #A is a public cloud environmentor the like, the extraction program 1170A may collect performancehistory using an I/F for configuration/performance informationacquisition which is used in cloud management, generate performancetrend information based on the collected performance historyinformation, and store the generated performance trend information andinformation on an allocated resource amount acquired using the I/F forconfiguration/performance information acquisition for each VM system.

FIG. 14 is a flow chart of a performance related information sharingprocess 8300 (copy source).

The performance related information sharing process 8300 (copy source)is a process at the copy source site of sharing performance relatedinformation extracted by the extraction program 1170A with a managementserver of a copy destination site. The present process is repetitively(for example, periodically) performed by the sharing program 1180A.

First, the sharing program 1180A refers to the configuration table1111A, acquires pair information (step 8301), and determines whether ornot there is one or more pieces of pair information (step 8302). When aresult of the determination in step 8302 is negative, the process isended.

When a result of the determination in step 8302 is positive, the sharingprogram 1180A performs step 8303 (loop D) for each site of a pairdestination. Specifically, for a pair destination site, the sharingprogram 1180A acquires performance trend information of a system using apair destination VOL of the pair destination site and resourceallocation information from the extraction program 1170A and transmitsthe acquired performance trend information and resource allocationinformation to the management server of the pair destination site (step8303).

While the performance related information sharing process 8300 is to beperiodically executed in this case, only information usable for resourceadjustment at a pair destination site may be transmitted only at atiming at which the information can be used. For example, the sharingprogram 1180A may store already-transmitted information and, withrespect to information unchanged from already-transmitted informationamong the pieces of information in the performance trend table, may notexecute the present process and adjust a timing such that, for example,information is not newly transmitted to a management server (forexample, 1000B) of a copy destination. In addition, for example, inaccordance with function information collected during pair creation, thesharing program 1180A may transmit only information necessary forrecreating an operation at a copy destination such as transmitting onlyinformation usable for changing resource allocation at a copydestination site (for example, B).

Furthermore, for example, in an environment where an increase in datatransfer amount does not pose a problem or the like, the sharing program1180A may transmit all of the information in the performance historytable 1121A to a management server (for example, 1000B) of a copydestination of each system. Moreover, at this point, the importance 121Ain accordance with an operation that runs on a system may also betransmitted for each system.

FIG. 20 is a flow chart of a performance related information sharingprocess 8600 (copy destination). In the following description, the copydestination is assumed to be the site #B.

The performance related information sharing process 8600 (copydestination) is a process of receiving performance related informationtransmitted from the copy source site #A in step 8303 shown in FIG. 14at the management server 1000B of the copy destination site #B. Thepresent process is performed by the sharing program 1180B.

First, the sharing program 1180B waits to receive performance relatedinformation of the system transmitted by the management server 1000A ofthe copy source and, when the performance related information isreceived, proceeds to step 8602.

In step 8602, the sharing program 1180B identifies the site ID 119B (forexample, “A”) corresponding to a storage ID 120B which matches anapparatus ID in the received performance related information from aconfiguration table 1111B. Next, the sharing program 1180B refers to atime point 132B in a related site table 1113B and, in accordance with atime point difference between the site #A and the site #B, changes avalue related to time in the performance related information(corresponds to the time 224 in the performance trend table) (step8603). Next, based on management format information 133B correspondingto the identified site ID 119B (for example, “A”), when the site #A andthe site #B have different management formats, the sharing program 1180Bconverts a data format of the performance related information from thecopy source site based on the difference in management formats (step8604), and stores the information in the received performance relatedinformation to a performance trend table 1122B and an allocated resourcetable 1123B (step 8605). As a result, performance related informationfrom the copy source site #A (first performance related information) andperformance related information in the copy destination site #B (secondperformance related information) are to exist in each of the performancetrend table 1122B and the allocated resource table 1123B. The secondperformance related information may be information related to a resourcerelated to an operation originally being executed at the copydestination site #B.

When the management formats introduced at the copy source and the copydestination are similar, normally, configurations of tables inmanagement servers (tables referred to or updated by managementprograms) are also similar. Therefore, shared data (informationtransmitted from the copy source site #A to the copy destination site#B) can be stored in tables without data format conversion.

On the other hand, when systems of different vendors are introduced atthe copy source site and the copy destination site or when the copysource site is a public cloud environment and the copy destination siteis a private cloud environment, different management formats are used bythe copy source site and the copy destination site. In this case,information stored at the respective sites has a different data formatand a different stored content. Since recent management programs oftenmake a data schema definition for storing performance historyinformation openly available, even when different management programsare being used, a performance related information sharing process can beperformed by preparing a program for converting a format of a dataschema to be stored in advance.

FIG. 15 is a flow chart of a pair configuration confirmation process8900.

The pair configuration confirmation process 8900 is a process performedduring normal operation of repetitively (for example, periodically)checking, at a copy source site, whether or not the system can beoperated without incident even when an operation is switched from thecopy source to the copy destination due to the occurrence of a disaster.Specifically, for example, confirmation that no functional problemsoccur even an operation is switched due to a disaster is repetitively(for example, periodically) made. The present process is performed bythe pair confirmation program 11D0A.

Since steps 8901 to 8904 performed by the pair confirmation program11D0A are similar processes to steps 8103 to 8106 shown in FIG. 12, adescription thereof will be omitted. When conditions are not satisfiedin step 8902 and step 8904, the pair confirmation program 11D0A notifiesthe user that an already-constructed pair no longer satisfies conditions(step 8905). In this case, while the pair confirmation program 11D0Anotifies that the pair no longer satisfies conditions, alternatively,the pair confirmation program 11D0A may notify that a change hasoccurred in configuration information to be a pair constructioncondition or in function information.

Alternatively, the pair confirmation program 11D0A may call the pairconfiguration destination selection process shown in FIG. 12 in place ofor in addition to the notification. For example, the pair confirmationprogram 11D0A may issue an alert (for example, display an alert) when aninquiry with respect to whether or not a same function as a functionenabled at the site #A is disabled or has been deleted at the site #B isrepetitively issued to the management server 1000B and a positiveresponse is received from the management server 1000B.

FIG. 16 is a flow chart of a resource adjustment scheme generationprocess 8400.

The resource adjustment scheme generation process 8400 is a process ofgenerating an adjustment scheme of a resource at the copy destinationsite B in consideration of an operation (a VM system) having migratedfrom the copy source site #A in accordance with an occurrence of adisaster and an operation (a VM system) originally running at the copydestination site #B. The present process 8400 is performed by theadjustment scheme generation program 1190B.

First, the adjustment scheme generation program 1190B adds up respectiveperformance level values and resource amounts related to VOLs of the VMsystem running at the copy destination site #B and the VM system havingmigrated from the copy source site #A. In this case, performance levelvalues are added up as time-series information.

For example, when considering performance trend as an example,performance level values of the VM system having migrated from the copysource site #A related to a CPU shared by the VOL #LV7 at the copysource and the VOL #LV11 at the copy destination are as shown in FIG. 8.Specifically, with respect to the VOL #LV7, the performance level valueis “0” at “00:00 to 08:00”, the performance level value is “1” at “08:00to 08:30”, the performance level value is “5” at “08:30 to 17:30”, andthe performance level value is “3” at “17:30 to 24:00”. With respect tothe VOL #LV8, the performance level value is “0” at “00:00 to 08:00”,the performance level value is “2” at “08:00 to 08:30”, and theperformance level value is “4” at “08:30 to 24:00”. On the other hand,for example, a performance trend of the VM system running at the copydestination site #B is as follows. Specifically, with respect to the VOL#LV11, the performance level value is “0” at “00:00 to 09:00”, theperformance level value is “1” at “09:00 to 012:00”, the performancelevel value is “3” at “12:00 to 17:30”, and the performance level valueis “2” at “17:30 to 24:00”. With respect to the VOL #LV12, theperformance level value is “3” at “00:00 to 24:00”. Therefore, resultsof an addition of performance level values for the respective time slotsare as follows.

Specifically, at “00:00 to 08:00”, the performance level value is “3”(=0+0+0+3), at “08:00 to 08:30”, the performance level value is “6”(=1+2+0+3), at “08:30 to 09:00”, the performance level value is “12”(=5+4+0+3), at “09:00 to 12:00”, the performance level value is “13”(=5+4+1+3), at “12:00 to 17:30”, the performance level value is “15”(=5+4+3+2), and at “17:30 to 24:00”, the performance level value is “12”(=3+4+2+3).

Next, with respect to components having a performance dependencerelationship with a VOL of the VM system having migrated from the copysource site A due to the disaster, the adjustment scheme generationprogram 1190B adds up performance level values and resource amountsrelated to respective components sharing resources of the migrated VMsystem and the VM system running at the copy destination site #B.Examples of a component having a performance dependence relationshipinclude a VM using the VOL and a logical space which is a source of theVOL. For example, let us assume that the copy source has the VM #5, theVM #7, and the VM #8 which are migration targets while the copydestination has the VM #11 and the VM #12. Resource amounts of the VMsystems are as shown in FIG. 9. Specifically, with respect to the copysource site #A, two CPU cores and a memory amount of 8 GB are allocatedas resources to the VM #5, two CPU cores and a memory amount of 8 GB areallocated as resources to the VM #7, and four CPU cores and a memoryamount of 16 GB are allocated as resources to the VM #8. With respect tothe copy destination site #B, four CPU cores and a memory amount of 16GB are allocated as resources to the VM #11 and four CPU cores and amemory amount of 16 GB are allocated as resources to the VM #12. Theseare added up. Therefore, addition results are as follows. Specifically,with respect to the shared server #B, the number of CPU cores is “16”(=2+2+4+4+4) and the memory amount is “64” (=8+8+16+16+16). In thiscase, while a server sharing resources is defined in advance, aplurality of servers usable by the VM system having migrated from thecopy source site #A may exist at the copy destination site #B, in whichcase a similar calculation may be performed for each server for a casewhere the server is shared. Furthermore, in addition to servers,addition may only be performed on shared resources defined in advanceamong shared resources such as the CPU 2500 and the storage I/F 2600,and when a selection can be made during the migration of the VM systemto the copy destination site #B, a calculation may be performed on eachshared resource at the copy destination site #B.

Next, the adjustment scheme generation program 1190B refers to aresource amount table 1124B and acquires an amount of hardware resourcesthat are monitoring targets used by the VOL and by components having aperformance dependence relationship with the VOL (step 8402).

The adjustment scheme generation program 1190B compares the additionvalues of the performance level values and resource amounts obtained instep 8401 with the resource amounts obtained in step 8403 (step 8403).

When the addition values do not exceed the resource amounts, theoperation may be restarted using the copy destination. Therefore, theadjustment scheme generation program 1190B determines that resourceadjustment is not necessary with respect to the copy destination site #Band ends the present process 8400. For example, while the additionvalues obtained in step 8401 with respect to the site #B are the numberof CPU cores “16” and the memory amount “64”, the resource amountsacquired in step 8402 are the number of CPU cores “8” and the memoryamount “16”. Since both the number of CPU cores and the memory amountexceed the resource amounts, processes of step 8404 and thereafter areto be performed.

When the addition values exceed the resource amounts, the adjustmentscheme generation program 1190B determines whether or not there isusable free space in a target (for example, a component/resource) of asame type as the monitoring target which is assigned a resource of asame type as a resource used by a component having a performancedependence relationship with the VOL (step 8404). When a result of thedetermination in step 8404 is positive, the adjustment scheme generationprogram 1190B generates an adjustment scheme which uses the target (step8405). For example, when a logical space 2220B is shared and theaddition value obtained in step 8401 exceeds a resource amount of thelogical space, the adjustment scheme generation program 1190B determineswhether or not there is free space in another logical space andgenerates an adjustment scheme (for example, a scheme to perform datamigration to a logical space having free space in its resources). Indoing so, when there is a free resource in a system operable at anothersite in the VM system having been running at the copy destination site#B, a resource of another site may be used by consecutively changingsites to be used.

Next, the adjustment scheme generation program 1190B acquiresinformation on tasks using a physical resource of which an additionamount exceeds a resource amount from the task table 1130B anddetermines whether or not there is a task which enables a processingtiming to be adjusted (step 8406). At this point, tasks due to userinput such as a configuration of VM migration based on operationalcircumstances and a backup configuration based on an operation policy ofa corporation may be determined not adjustable while tasks executedinside an apparatus such as defragmentation may be determinedadjustable. However, these are not restrictive and in the case of aresource related to a server being used in a system of which theimportance 121A is high (for example, importance is “High”), anothertask executed at a time point at which the resource amount is exceededmay be unconditionally determined to be adjustable. When a result of thedetermination in step 8406 is positive, the adjustment scheme generationprogram 1190B generates an adjustment scheme of task execution contents(step 8407). For example, the adjustment scheme generation program 1190Bchecks whether or not the sum (addition value) of performance levelvalues obtained in step 8401 exists at a time during which a separatelyexecuted task such as a periodically executed virus scanning process ora backup process exceeds a resource amount and generates an adjustmentscheme which changes a schedule so that the process is executed in adifferent time slot. Moreover, the generation of an adjustment scheme instep 8407 may be performed only when an adjustment scheme cannot begenerated in step 8405 or may be performed even when step 8405 has beenperformed.

Subsequently, the adjustment scheme generation program 1190B generatesan adjustment scheme which adjusts resource allocation amounts of thesystem having migrated from the copy source site due to the disaster andthe system of the copy destination site B while maintaining anallocation ratio of each system (step 8408). At this point, by usinginformation in the performance trend table 1122B shown in FIG. 8 or theresource amount table 1124B shown in FIG. 9, information on a resourceamount ratio at each server, which is necessary to operate a systemdesigned at the copy source site #A (or a system accumulated throughoperations at the copy source site #A) without incident, can beutilized. Moreover, the generation of an adjustment scheme in step 8408may be performed only when an adjustment scheme cannot be generated inboth step 8405 and step 8407 or may be performed even when any of step8405 and step 8407 has been performed.

For example, in the example described with reference to step 8401, withrespect to a CPU shared by the VOL #LV7, the VOL #LV8, the VOL #LV11,and the VOL #LV12, a performance level value of “3” for “00:00 to08:00”, a performance level value of “6” for “08:00 to 08:30”, aperformance level value of “12” for “08:30 to 09:00”, a performancelevel value of “13” for “09:00 to 12:00”, a performance level value of“15” for “12:00 to 17:30”, and a performance level value of “10” for“17:30 to 24:00” are respectively obtained. A maximum usage thereof isthe performance level value “15” (Max 150 K) for “12:00 to 17:30”. Inthis example, usage of the CPU is 80 K (not shown).

In this case, the adjustment scheme generation program 1190B generates ascheme for performing resource adjustment so that the VOL #LV7 and theVOL #LV8 and the VOL #LV5, and the VOL #LV11 and the VOL #LV12 whichconstitute a 1VM system respectively maintain a same resource usageratio. In the case of this example, by uniformly reducing an I/O amountusing the CPU by 50%, the IOPS can be brought down to 75 K or lower andusage of the CPU can be kept to 80 K or lower. While IOPS is uniformlyreduced by 50% in this case, alternatively, reduction amounts may differ(may be weighted) according to systems such as applying a reduction by20% to a system with high priority, a reduction by 40% to a system withmiddle priority, and a reduction by 70% to a system with low priority inaccordance with (a) an importance transmitted from the copy source sitein the performance related information sharing process (an importance ofeach system) or (b) an importance managed separately across sites inadvance (an importance of each system). Moreover, at this point,adjustment schemes may be narrowed down by checking to see whether ornot a value as a result of reducing the resource amount is larger than aminimum operation value 225B of the performance trend table 1122B and,if not, a scheme is not generated since requirements are not satisfied.

While the minimum operation value 225B is prepared only in theperformance trend table 1122B in this case, the resource amount table1124B may also be provided with a column for a minimum operation valueand a necessary minimum memory capacity or the like may be stored,whereby the necessary minimum memory capacity may be used as anarrowing-down condition when generating adjustment schemes in thepresent step 8409.

Furthermore, for example, the adjustment scheme generation program 1190Bcombines and stores adjustment schemes of each resource generated insteps 8405, 8407, and 8408 in a resource adjustment scheme table 1140B(step 8409), and ends the resource adjustment scheme generation process8400. Since the resource adjustment scheme table 1140B storesinformation similar to those on an adjustment scheme screen 9100B to bedescribed later, a description thereof will be omitted.

FIG. 17 is a flow chart of a resource adjustment process 8500.

The pair configuration confirmation process 8500 is a process ofpresenting adjustment schemes generated by the adjustment schemegeneration program 1190B, accepting an input, and executing anadjustment scheme. The present process is performed by an adjustmentscheme presentation program 11A0B.

First, the adjustment scheme presentation program 11A0B refers to theresource adjustment scheme table 1140B (step 8501). Next, the adjustmentscheme presentation program 11A0B determines whether or not there areone or more resource adjustment schemes (step 8502).

When a result of the determination in step 8502 is positive, theadjustment scheme presentation program 11A0B presents the resourceadjustment schemes to the user via an output device 1400B and accepts aninput regarding which is to be executed among the resource adjustmentschemes (step 8503). Based on the input, the adjustment schemepresentation program 11A0B transmits an execution request to a resourceadjustment program 11B0B or a task adjustment program 11C0B (step 8504).Alternatively, the presentation of adjustment schemes may be skipped andstep 8504 may be performed after a resource adjustment scheme is inputor automatically selected according to a policy such as “Prioritize taskadjustment processing” and “Prioritize use of available resource”.

When the result of the determination in step 8502 is negative, whenthere is no input for a prescribed time in step 8503 or when there is aninput to end the resource adjustment process in step 8503, theadjustment scheme presentation program 11A0B notifies the user of awarning that the system is to be stopped (or a warning of a possibilitythat the system may not operate normally) (step 8505).

FIG. 18 is a configuration diagram of an adjustment scheme screen 9100B.

The adjustment scheme screen 9100B is a screen which is presented instep 8501 shown in FIG. 17. The screen 9100B includes a display area9101B showing a list of resource adjustment schemes to be candidates ofexecution, a display area 9102B showing information on systems to beaffected when a resource adjustment scheme is executed, a display area9103B showing information on components to be affected when a resourceadjustment scheme is executed, a display area 9104B showing affectedcontents of the components to be affected, an adjustment scheme detailbutton 9107B for displaying details of a resource adjustment scheme, andan adjustment scheme execution button 9108B for executing an adjustmentscheme. The display area 9104B showing affected contents of thecomponents to be affected includes a display area 9105B showing anaffected metric and a display area 9106B showing a degree of effect.

In the present embodiment, the list of resource adjustment schemesincludes an adjustment scheme 1 for only performing a resourceallocation change, an adjustment scheme 2 for performing a resourceallocation change and performing a task schedule change, and anadjustment scheme 3 for performing a VOL migration and a VM migration.Performance is not affected in the case of the adjustment scheme 2 andthe adjustment scheme 3. Therefore, the screen 9100B does not presentinformation regarding the affected metric 9105B and the effect 9106B andrespectively shows an effect that a start time point of a task is to bechanged and an effect that a physical resource used by a VOL or a VM isto be changed as the affected contents 9104B.

In this case, an order of arrangement of the adjustment schemes may bean order based on features of the adjustment schemes such as adescending order of estimated values when assuming that the adjustmentschemes are executed or an ascending order of times required to executethe adjustment schemes. In addition, while specific amounts of changeare shown as the degree of effect 9106B of the affected contents 9104Bin the present embodiment, this is not restrictive and the degree of theeffect may be displayed using multilevel symbols such as “o”, “A”, and“x”. Furthermore, while a VOL and a VM are presented as affectedcomponents in the present embodiment, other values such as a logicalspace and other components may be displayed. In addition, while an IOPS,a CPU, and a memory are presented as affected metrics, other values suchas an I/O response time and other metrics may be displayed.

FIG. 19 is a configuration diagram of an example of an adjustment schemedetail screen 9200B.

The present screen 9200B is a screen that is displayed when any of theadjustment schemes in the display area 9101B showing the list ofadjustment schemes is selected and the adjustment scheme detail button9107B is subsequently pressed on the adjustment scheme screen 9100Bshown in FIG. 18. The screen 9100B shows detail information of aselected adjustment scheme.

The adjustment scheme detail screen 9200B includes a display area 9201Bshowing a list of resource adjustment schemes to be candidates ofexecution, a display area 9202B showing information on systems to beaffected when a resource adjustment scheme is executed, a display area9203B showing a change in a resource allocation amount to a storageaccompanying resource adjustment, a display area 9204B showing a changein a resource allocation amount to a server, and an adjustment schemeexecution button 9210B for executing an adjustment scheme. The displayareas 9203B and 9204B include display areas respectively showing an IDof a monitoring target of which an allocation amount of a resourcechanges (9204B, 9208B), an ID of a monitoring target which retains anallocated resource (9205B, 9209B), and an amount of change in anallocated resource (9206B, 9210B, and 9211B). In the present embodiment,the adjustment scheme screen 9100B in FIG. 18 shows an example in whicha “resource allocation change scheme” displayed at the top of theresource adjustment scheme candidates (display area) 9101B. The presentexample represents an example of a performance trend of three VOLs (LV5,LV7, and LV8) used by a system Y running at the copy source site Awhere, due to a change in resource allocation, from respective originalmaximum IOPS of 20 K, 50 K, and 40 K, usage is limited in half to 10 K,25 K, and 20 K. In addition, an example is shown of a performance trendof two VOLs (LV11 and LV12) used by a system B running at the copydestination site B where, from respective original maximum IOPS of 30 K,usage is limited in half to 15 K. As a method of applying a limit toresource use, any method may be adopted such as using a function of astorage apparatus or including an ID of an I/O destination VOL in an I/Orequest from a server (host). Furthermore, an example is shown of aperformance trend of three VMs (VM5, VM7, and VM8) used by the system Yrunning at the copy source site A where virtual CPUs are respectivelyreallocated at half and virtual memories are respectively reallocated at¼. Moreover, an example is shown of a performance trend of two VMs (VM11and VM12) used by the system B running at the copy destination site Bwhere virtual CPUs are respectively reallocated at half and virtualmemories are respectively reallocated at ¼. In this case, resourceadjustment is performed so as to fall within the values shown in theresource amount table in FIG. 10. While an example of adjusting a CPUresource, a memory amount, and an IOPS amount that can be processed by aCPU has been shown in FIGS. 18 and 19 in the present embodiment,resource adjustment is not limited thereto.

Alternatively, for example, a configuration may be adopted in whichchanges due to adjustment are displayed in a time-sequential stackedgraph format in the display area 9104B showing affected contents in FIG.18, the display area 9203B showing a change in a resource allocationamount to a storage in FIG. 19, and the display area 9204B showing achange in a resource allocation amount to a server in FIG. 19.

FIGS. 18 and 19 represent examples of screens and, as effects caused bythe execution of an adjustment scheme, information representing othercharacteristics may also be displayed such as information on a timerequired to execute the adjustment scheme, a cost required to executethe adjustment scheme, a cost per unit time required for configurationafter executing the adjustment scheme, and an expected duration of theconfiguration without changes thereto after executing the adjustmentscheme. Accordingly, a manager can make a selection based on his or herown criteria from a plurality of resource adjustment schemes withdifferent characteristics. In addition, the information can also bereferred to as an index regarding how much time and cost need to bedevoted for the recovery of a copy source site.

According to the embodiment described above, by extracting a performancetrend and a resource usage ratio of systems from performance informationof a copy source site #A related to a pair and repetitively (forexample, periodically) sharing the performance trend and the resourceusage ratio with a management server 1000B of a copy destination site#B, resource adjustment can be performed at the copy destination site #Bupon an occurrence of a disaster in consideration of an operation havingmigrated due to the occurrence of the disaster and an operationoriginally running at the copy destination site #B. As a result, whencontinuing an operation of a disaster-affected site at the copydestination site #B, a decline in performance of the operation can bemitigated.

While an embodiment has been described above, it is to be understoodthat the described embodiment merely represents an example forillustrating the present invention and that the scope of the presentinvention is not limited to the embodiment. The present invention can beimplemented in various other modes.

REFERENCE SIGNS LIST

-   1000 Management server-   2000 Storage apparatus-   3000 Server

1. A management system, comprising: an interface device coupled to atleast a second computer system among a plurality of sites including afirst site which includes a first computer system and a second sitewhich includes the second computer system; a storage unit configured tostore management information including second performance relatedinformation; and a processor coupled to the interface device and thestorage unit, the first computer system being configured to have a firstresource group, execute a first operation, and provide a plurality oflogical volumes which include a first logical volume to be an I/Odestination of the first operation, the second computer system beingconfigured to have a second resource group, execute a second operation,and provide a plurality of logical volumes which include a secondlogical volume that is a copy destination of the first logical volumeand a third logical volume to be an I/O destination of the secondoperation, the second performance related information includinginformation related to a resource related to the second operation amongthe second resource group, and the processor being configured to:receive first performance related information including informationrelated to a resource, among the first resource group of the first site,related to the first operation which the first logical volume that is acopy source of the second logical volume is associated as I/Odestination; store the received first performance related information inthe storage unit; and when the first operation migrates from the firstsite to the second site, perform reallocation of resources of the secondsite based on both the first performance related information and thesecond performance related information.
 2. The management systemaccording to claim 1, wherein the first performance related informationincludes first performance trend information which is informationincluding a performance level value of a component related to a resourcerelated to the first operation and a time to which the performance levelvalue belongs, the second performance related information includessecond performance trend information which is information including aperformance level value of a component related to a resource related tothe second operation and a time to which the performance level valuebelongs, and the processor is configured to: perform a calculation usinga performance level value identified from the first performance trendinformation and a performance level value identified from the secondperformance trend information based on a time identified from the firstperformance trend information and a time identified from the secondperformance trend information; and perform the reallocation in a case ofexceeded resources which is a state where a value calculated as a resultof the calculation exceeds a threshold in accordance with a resourcerestriction of the second site.
 3. The management system according toclaim 2, wherein the first performance related information includesfirst allocated resource information which is information includinginformation representing an amount of resources related to the firstoperation for each resource type, the second performance relatedinformation includes second allocated resource information which isinformation including information representing an amount of resourcesrelated to the second operation for each resource type, and theprocessor is configured to refer to the first allocated resourceinformation and the second allocated resource information and performthe reallocation such that a resource amount ratio related to the firstoperation and a resource amount ratio related to the second operationare both maintained.
 4. The management system according to claim 1,wherein the processor is configured to: generate one or morereallocation schemes based on both the first performance relatedinformation and the second performance related information; display theone or more reallocation schemes; and receive a selection of anexecution target reallocation scheme among the one or more reallocationschemes, the reallocation being a reallocation in accordance with areallocation scheme corresponding to the received selection.
 5. Themanagement system according to claim 4, wherein the managementinformation includes configuration information which is informationrelated to a configuration of at least the second resource group among aplurality of resource groups respectively included in the plurality ofsites, and the processor is configured to: determine whether or not ausable free resource related to a component of a same type as acomponent related to the first operation and the second operation existsin a target resource group which is a resource group of any site otherthan the first site based on the configuration information, the firstperformance related information and the second performance relatedinformation; and generate a component migration as a reallocation schemewhen a result of the determination is positive, the component migrationis to associate, in place of a resource associated with at least onecomponent of a same type, the usable free resource in the targetresource group with the at least one component of a same type.
 6. Themanagement system according to claim 4, wherein the processor isconfigured to: determine whether or not there is a task of which anexecution start timing can be changed among one or more tasks using aresource corresponding to the threshold related to the exceededresources; and when a result of the determination is positive, generatea reallocation scheme including changing the execution start timing ofthe task of which the execution start timing can be changed to any timepoint other than a time corresponding to the exceeded resources.
 7. Themanagement system according to claim 1, wherein the reallocation is torespectively reduce an amount of resources allocated to the firstoperation as a component and an amount of resources allocated to thesecond operation as a component while maintaining both a resource amountratio related to the first operation and a resource amount ratio relatedto the second operation.
 8. The management system according to claim 7,wherein a migration target is a first operation system which is a set ofone or more operations including the first operation, the secondcomputer system is configured to be executing a second operation systemwhich is a set of one or more operations including the second operation,and the processor is configured to determine an amount of reduction of aresource amount allocated to the first operation system and an amount ofreduction of a resource amount allocated to the second operation systembased on an importance of the first operation system and an importanceof the second operation system.
 9. The management system according toclaim 1, comprising: a first management computer which manages the firstcomputer system and which is included in the first site; and a secondmanagement computer which manages the second computer system and whichis included in the second site, wherein the second management computerincludes the interface device, the storage unit, and the processor, thefirst management computer is configured to store first managementinformation which is management information including informationrelated to a pair of logical volumes, and the first management computeris configured to select, based on the first management information, thesecond management computer in the second site including the secondlogical volume which constitutes a pair with the first logical volume asa transmission destination of first performance related informationincluding information related to a resource related to the firstoperation having the first logical volume as an I/O destination.
 10. Themanagement system according to claim 9, wherein the first performancerelated information does not include information related to a resourcerelated to operations not migrated to the second site among the firstresource group.
 11. The management system according to claim 9, whereinthe first management information includes information representing anenabled function among functions retained by the first site andfunctions retained by each site other than the first site, the firstmanagement computer is configured to: identify one or more sites havinga same function as the function enabled at the first site based on theconfiguration information; and display information related to the one ormore identified sites, the second site is a site selected from the oneor more displayed sites, and the second logical volume is a logicalvolume selected from the plurality of logical volumes included in thesecond site.
 12. The management system according to claim 11, whereinthe first management computer is configured to: repetitively issue aninquiry about whether or not a same function as the function enabled atthe first site is disabled or has been deleted at the second site to thesecond management computer; and issue an alert when a positive responseis received.
 13. The management system according to claim 1, wherein theprocessor is configured to update the management information, theupdated management information indicates that, with respect to a samefunction as the function enabled at the first site among functionsincluded in the second site, the function is enabled and a same functionas the function is also enabled at another site having the second siteas an operation migration destination, when an indication to disable ordelete a function is received, the processor is configured to: determinewhether or not a function corresponding to the received indication isenabled and a same function as the function is also enabled at anothersite having the second site as an operation migration destination basedon the management information; and issue an alert when a result of thedetermination is positive.
 14. The management system according to claim1, wherein the management information includes information representinga first management format which is a management format of at least afirst site among the plurality of sites, and the processor is configuredto: receive the first performance related information from the firstsite; determine whether or not the first management format and a secondmanagement format which is a management format at the second site differfrom each other based on the management information; when a result ofthe determination is positive, convert the first performance relatedinformation based on a difference between the first management formatand the second management format; and store the converted firstperformance related information in the storage unit.
 15. A managementmethod of at least a second computer system among a plurality of sitesincluding a first site which includes a first computer system and asecond site which includes the second computer system, the firstcomputer system being configured to have a first resource group, executea first operation, and provide a plurality of logical volumes whichinclude a first logical volume to be an I/O destination of the firstoperation, the second computer system being configured to have a secondresource group, execute a second operation, and provide a plurality oflogical volumes which include a second logical volume that is a copydestination of the first logical volume and a third logical volume to bean I/O destination of the second operation, and the management methodcomprising: receiving first performance related information includinginformation related to a resource, among the first resource group of thefirst site, related to the first operation with which the first logicalvolume that is a copy source of the second logical volume is associatedas I/O destination; storing the received first performance relatedinformation; and when the first operation migrates from the first siteto the second site, performing reallocation of resources of the secondsite based on both the first performance related information and secondperformance related information which includes information related to aresource related to the second operation among the second resourcegroup.